In this article we will review important details as for Project Online <> Jira data synchronization and known limitations for this scenario.
Please note: Master Projects are not supported for integrations.
Please note: Integration Hub supports the company-managed Jira project type only.
Fields mapping table
The table below indicates possible field mappings and mapping directions.
| Project Online | Integration direction | JIRA |
| Custom field: Task.“Jira Issue Type” | ⇔ | System field: Issue.IssueType |
| System field: Task.Name | ⇔ | System field: Issue.Summary |
| System field: UnassignedTask.Work | → | System field: Issue.Estimated |
| System field: UnassignedTask.ActualWork | ⇐ | System field: Issue.Logged |
| System field: UnassignedTask.RemainingWork | ⇔ | System field: Issue.Remaining |
| System field: Task.Assignment | ⇔ | System field: Issue.Assignment |
| System field: Task.Assignment.Work | → | System field: Issue.Estimated |
| System field: Task.Assignment.ActualWork | ⇐ | System field: Issue.Logged |
| System field: Task.Assignment.RemainingWork | ⇔ | System field: Issue.Remaining |
| System field: Task.FinishDate | ⇔ | System field: Issue.DueDate |
| System field: Task.Assignment.ActualStart | ⇐ | System field: Issue.WorkLog.DateStarted |
| Hierarchy: Task.ParentTaskId | ⇔ | Hierarchy: Issue.ParentIssueId |
Legend:
⇔ Data can be synced in both directions
⇐ Data can be synced only in one direction
< Data can be synced only at the first migration of the Entity (On create)
→ Data can be synced only at the first migration of the Value of some parameter (On update)
Data transfers specific
Sibling tasks
Unlike Project Online, Jira doesn’t allow multiple assignments on one task. During an integration, if a task with multiple assignments is found in Project Online, it will be transformed into multiple issues with the same name, assigned respectively.
Task assignments can be transferred from Project Online to Jira if:
- A work non-generic resource is assigned to it;
- That resource has the "Email" field populated (from AD sync or manually);
- There's a valid account in Jira that corresponds to such a resource, and email in Jira is identical to that in Project Online;
- The account settings in Jira are configured to expose the email to "Everyone".
When synchronizing resources to/from Jira, resource accounts may not be synchronized due to Jira API limitations. To sync accounts to/from Jira it is required to make all accounts that take part in data synchronization visible to anyone who can view your content and accessible by installed apps. For this purpose open the Account settings => Profile and visibility => Anyone.
The setting should be set to Anyone before the synchronization process begins.
When a task with multiple resources is synced, on Jira side multiple issues with identical names but respective assignments are created. On the sync from Jira into Project Online all reported time will be added into a single value for completed work. If an assignment is dropped in Project Online, the respective Jira issue is renamed to mark it for deletion.
Actual start – is the date when the time was tracked on the issue for the first time.
Please note: If the "Only allow task updates via Tasks and Timesheets" option is activated in Project Online, the integration will not work. If you are using the Integration Hub to synchronize Actual hours from Jira to Project Online, you will need to switch off the "Only allow task updates via Tasks and Timesheets" option before the integration and switch it back on manually after the integration is completed.
Sub-task transfer specific
To transfer the summary tasks with their sub-tasks from Jira to Project Online and vice versa correctly, you need to stick to the following simple rules.
Start/Due dates are not migrated for sub-tasks.
Project Online > Jira direction
- Your summary task should have at least one sub-task.
- Your summary task shouldn’t have any assignments. Assignments should only be set for the sub-tasks.
- The Jira Issue Type field for the summary task should have any value (Task, Bug, etc.) except for Sub-task.
- The Jira Issue Type field for all the sub-tasks should be set to Sub-task.
- The Sync to Jira field should be set to Yes for all the summary and sub-tasks you want to synchronize:
- If the Sync to Jira field for the summary task is set to No, its sub-tasks are also not transferred regardless of their settings:
- If the Sync to Jira field is set to No for all the sub-tasks, Integration Hub also ignores the summary task:
Jira > Project Online direction
- Your summary task should have at least one sub-task.
- Your summary task shouldn’t have any assignments. Assignments should only be set for the sub-tasks.
- The Sync with Project Online field should be set to Yes for all summary and sub-tasks you want to synchronize.
- If the Sync with Project Online field is set to No for all the sub-tasks and to Yes for the summary task, Integration Hub still transfers the summary task to Project Online, however, it is converted to a common task.
- Changing issue type on the same hierarchy level (e.g. Bug to Task) is allowed. However, changing the issue type along with its hierarchy level (e.g. converting a Task to a Sub-task) may and will lead to various problems with your sync.
